Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct formatting for TaskRun in Build docs #85708

Closed

Conversation

likhithj1996
Copy link

@likhithj1996 likhithj1996 commented Dec 3, 2024

Version(s):

builds-docs-1.1andbuilds-docs-1.0

Issue:

https://issues.redhat.com/browse/RHDEVDOCS-6154

Link to docs preview:

BuildRun Resource

QE review:

  • QE has approved this change.

QE review:
SME review:
Peer review:
Internal Peer review: @Dhruv-Soni11

Additional information:

@openshift-ci openshift-ci bot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Dec 3, 2024
@ocpdocs-previewbot
Copy link

ocpdocs-previewbot commented Dec 3, 2024

🤖 Wed Dec 11 13:30:36 - Prow CI generated the docs preview:

https://85708--ocpdocs-pr.netlify.app/openshift-builds/latest/about/overview-openshift-builds.html

@Dhruv-Soni11
Copy link
Contributor

/lgtm, thanks @likhithj1996.

Kindly add the correct hyperlink of the affected section in the PR description and do not copy-paste the automated preview link. The change was made in the buildrun resource section but you have pasted a link for the Overview of builds section, which is incorrect.

@likhithj1996
Copy link
Author

@Dhruv-Soni11 Thanks Dhruv. I have updated the PR with the correct preview link.

@kalexand-rh kalexand-rh requested a review from shipsing December 10, 2024 14:20
@shipsing
Copy link
Contributor

shipsing commented Dec 11, 2024

@likhithj1996, for clarity purpose: It is not always necessary to put TaskRun or BuildRun in backticks. The cases where we want to refer these entities in generic manner, we can simply write task run or build run. You need to use backticks only when you refer those entities as objects or resources. for example, A BuildRun resource invokes a build on your cluster, similar to any cluster job or Tekton task run. In the sentence, BuildRun needs backticks because we are referring it as a resource, but task run is used in generic manner (no need of backticks).

You can refer to this link to see pipeline run instances that do not use backticks.

I do not think we should put task run in backticks in this context.

Copy link

openshift-ci bot commented Dec 11, 2024

@likhithj1996: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/validate-portal 9fd871b link true /test validate-portal

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@shipsing
Copy link
Contributor

@likhithj1996, I would suggest to close this PR and the issue. There is no need to change anything in the task run formatting.

@@ -6,7 +6,7 @@
[id="about-buildrun_{context}"]
= BuildRun resource

A `BuildRun` resource invokes a build on your cluster, similar to any cluster job or Tekton task run. The `BuildRun` resource represents a workload on your cluster, which results in a running pod. A `BuildRun` is the running instance of a build. It instantiates a build for execution with specific parameters on a cluster.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@likhithj1996, here the TaskRun is referred in a generic way, that is, task run. So, no need to change its formatting. Please close the PR, the original formatting here is correct.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the explanation in simple and clear way. I agree and will be closing the PR and the JIRA ticket. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants